Retracting shortcut bars, status shortcuts and edit run page sets

ABSTRACT

At least one example embodiment discloses a method for generating a touch screen display. The method includes establishing a run screen on the touch screen display, the run screen associated with a function of a work vehicle, configuring the run screen with a retractable toolbar, the retractable toolbar responsive to an action of a user of the touch screen display and deployable over a first portion of the run screen upon the action of the user and otherwise hiding to display a second portion of the run screen, the second portion of the run screen being at least a majority portion of the run screen and defining one or more transient user-definable buttons on the retractable toolbar associated with at least one of the function and the run screen.

PRIORITY

This non-provisional application claims priority under 35 U.S.C. §119 toprovisional application No. 61/806,642 filed Mar. 29, 2013; the entirecontents of which are hereby incorporated by reference.

FIELD

Example embodiments are related to displays including touch screendisplays for work vehicles such as off-road work vehicles, agriculturalmachines, forestry machines, construction machines and heavy equipment.

BACKGROUND

Many work vehicles include displays for displaying a status of thevehicle and various functions of the vehicle. Many of these displays areoperated by physical buttons and subject to requirements set by astandard.

SUMMARY

At least one example embodiment discloses a retractable shortcut bar fora touch screen display. The retractable shortcut bar may be a componentlocated at a bottom of a screen. The retractable shortcut bar may serveas a container for shortcut buttons serving various user interfacefunctions.

At least one example embodiment discloses an edit run page set overlay.The edit run page set overlay may include design components for editinga current run page set. The edit run page set overlay gives the user theability to change the name of the current run page set and to add,remove, and reorder pages within the run page set.

At least one example embodiment discloses a status shortcut for a touchscreen display. The status shortcut is a component that may be locatedon a shortcut bar. The status shortcut allows an operator to observeand/or toggle the status of an application feature without opening theapplication.

At least one example embodiment discloses a method for generating atouch screen display. The method includes establishing a run screen onthe touch screen display, the run screen associated with a function of awork vehicle, configuring the run screen with a retractable toolbar, theretractable toolbar responsive to an action of a user of the touchscreen display and deployable over a first portion of the run screenupon the action of the user and otherwise hiding to display a secondportion of the run screen, the second portion of the run screen being atleast a majority portion of the run screen and defining one or moretransient user-definable buttons on the retractable toolbar associatedwith at least one of the function and the run screen.

At least one example embodiment discloses a method for managing adisplay of a display system. The method includes establishing a runscreen associated with a first function of a work vehicle, providing alocation-determining receiver for potential guidance of the workvehicle, establishing a plurality of performance states associated withat least one of the location-determining receiver and a guidancecontroller and displaying one or more of the performance states bycorresponding visually displayable states without changing to anotherscreen of the display.

At least one example embodiment discloses a method for generating atouch screen display. The method includes establishing a first runscreen associated with a first function of a work vehicle andestablishing a second run screen associated with a second function ofthe work vehicle distinct from the first function and defining an orderof appearance of the first run screen and the second run screen within aset of run screens that allows a user to select a run screen in the setof run screens that are displayable in accordance with the definedorder.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments will be more clearly understood from the followingdetailed description taken in conjunction with the accompanyingdrawings. FIGS. 1-11E represent non-limiting, example embodiments asdescribed herein.

FIG. 1A illustrates a vehicle according to an example embodiment;

FIG. 1B illustrates a system of a vehicle according to an exampleembodiment;

FIGS. 2A-2B illustrate a set of run pages for ten inch screen accordingto an example embodiment;

FIGS. 3A-3B illustrate a set of run pages for seven inch screenaccording to an example embodiment;

FIG. 4A illustrates an example embodiment of a screen with a shortcutbar retracted;

FIGS. 4B-4C illustrate example embodiments of a screen with a shortcutbar extended;

FIGS. 5A-5E illustrate an example embodiment of a status shortcutbutton;

FIG. 6 illustrates a menu according to an example embodiment;

FIGS. 7A-7C illustrate a layout manager according to an exampleembodiment;

FIG. 8 illustrates a select dashboard display according to an exampleembodiment;

FIGS. 9A-9C illustrate run page set displays according to an exampleembodiment;

FIGS. 10A-10J illustrates an example embodiment of adding and editing arun page; and

FIGS. 11A-11E illustrates an example embodiment of adding and editing ashortcut bar.

DETAILED DESCRIPTION

Various example embodiments will now be described more fully withreference to the accompanying drawings in which some example embodimentsare illustrated.

Accordingly, while example embodiments are capable of variousmodifications and alternative forms, embodiments thereof are shown byway of example in the drawings and will herein be described in detail.It should be understood, however, that there is no intent to limitexample embodiments to the particular forms disclosed, but on thecontrary, example embodiments are to cover all modifications,equivalents, and alternatives falling within the scope of the claims.Like numbers refer to like elements throughout the description of thefigures.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another. For example, a first element could be termed asecond element, and, similarly, a second element could be termed a firstelement, without departing from the scope of example embodiments. Asused herein, the term “and/or” includes any and all combinations of oneor more of the associated listed items.

It will be understood that when an element is referred to as being“connected” or “coupled” to another element, it can be directlyconnected or coupled to the other element or intervening elements may bepresent. In contrast, when an element is referred to as being “directlyconnected” or “directly coupled” to another element, there are nointervening elements present. Other words used to describe therelationship between elements should be interpreted in a like fashion(e.g., “between” versus “directly between,” “adjacent” versus “directlyadjacent,” etc.).

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of exampleembodiments. As used herein, the singular forms “a,” “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises,” “comprising,” “includes” and/or “including,” when usedherein, specify the presence of stated features, integers, steps,operations, elements and/or components, but do not preclude the presenceor addition of one or more other features, integers, steps, operations,elements, components and/or groups thereof.

It should also be noted that in some alternative implementations, thefunctions/acts noted may occur out of the order noted in the figures.For example, two figures shown in succession may in fact be executedsubstantially concurrently or may sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which example embodiments belong. Itwill be further understood that terms, e.g., those defined in commonlyused dictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the relevant art andwill not be interpreted in an idealized or overly formal sense unlessexpressly so defined herein.

Portions of example embodiments and corresponding detailed descriptionare presented in terms a processor specifically programmed to executesoftware, or algorithms and symbolic representations of operation ondata bits within a computer memory. These descriptions andrepresentations are the ones by which those of ordinary skill in the arteffectively convey the substance of their work to others of ordinaryskill in the art. An algorithm, as the term is used here, and as it isused generally, is conceived to be a self-consistent sequence of stepsleading to a result. The steps are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of optical, electrical, or magneticsignals capable of being stored, transferred, combined, compared, andotherwise manipulated. It has proven convenient at times, principallyfor reasons of common usage, to refer to these signals as bits, values,elements, symbols, characters, terms, numbers, or the like.

In the following description, illustrative embodiments will be describedwith reference to acts and symbolic representations of operations (e.g.,in the form of flowcharts) that may be implemented as program modules orfunctional processes including routines, programs, objects, components,data structures, etc., that perform particular tasks or implementparticular abstract data types and may be implemented using existinghardware. Such existing hardware may include one or more CentralProcessing Units (CPUs), digital signal processors (DSPs),application-specific-integrated-circuits, field programmable gate arrays(FPGAs) computers or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, or as is apparent from the discussion,terms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical, electronicquantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission or display devices.

Note also that the software implemented aspects of example embodimentsare typically encoded on some form of tangible (or recording) storagemedium or implemented over some type of transmission medium. Thetangible storage medium may be magnetic (e.g., a floppy disk or a harddrive) or optical (e.g., a compact disk read only memory, or “CD ROM”),and may be read only or random access.

The term implement may refer to a particular piece of equipment orfunction of the vehicle including a plow, tillage equipment, harvestinghead, planter and sprayer.

FIG. 1A illustrates a vehicle 60 in which at least one exampleembodiment is implemented. The vehicle 60 includes a display system 105including a display 115. The display 115 may display any features orparameters of the vehicle 60, including, for example, speed and headinginformation. The display 115 may be used to enter user preferenceparameters described in further detail below. For example, the display115 may be used to establish a retracting shortcut bar, status shortcutsand edit run page sets.

Features of the display system 105 are described in further detail withregard to FIG. 1B.

FIG. 1B illustrates a system of a vehicle according to an exampleembodiment. The vehicle may be a work vehicle such as an off-road workvehicle, agricultural machine, forestry machine, construction machine orheavy equipment vehicle. However, example embodiments are not limitedthereto and may be implemented in other types of vehicles.

The system 100 includes electronic modules, software modules, or both.In an example embodiment, the system 100 includes a display system 105to support storing, processing or execution of software instructions ofone or more software modules. The display system 105 is indicated by thedashed lines in FIG. 1B. It should be understood that the system 100 mayinclude other systems configured to support storing, processing orexecution of software instructions of one or more software modules inthe functioning of the machine. However, for the sake of brevity, theywill not be described understanding that FIG. 1B is not limited just tothe features shown in FIG. 1B.

The lines that are interconnecting the aforementioned devices may bephysical data paths, logical data paths, or both. Physical data pathsare defined by transmission lines or data buses. Data buses may be, forexample, Control Area Network (CAN) buses or ISO buses. Logical datapaths may comprise logical or virtual communications that take placewithin software or between software modules.

The display system 105 is configured receive data regarding systems(e.g., steering system 212, braking system 214, propulsion system 216,vehicle sensor(s) 218), components and implements via a communicationsinterface 110 in the display system 105 that accesses a vehicle data bus210. The vehicle data bus 210 may be a controller area network (CAN)data bus, for example.

The communications interface 110 may receive and transmit messagescontaining further data to/from the vehicle data bus 210 such as, forexample, the steering system 212, braking system 214, propulsion system216, vehicle sensor(s) 218 or other controller of the vehicle connectedon the data bus. The messages may be implemented using a protocol suchas CAN. The messages may contain data including operational parametersor other parameters related to the vehicle provided by the sensors 218,for example, temperature gauges, magnetic wheel speed sensors, tractioncontrol sensors, etc.

Each of the steering system 212, braking system 214 and propulsionsystem 216 receives commands from and communicates data to a steeringcontroller 222, braking controller 224 and propulsion controller 226,respectively.

The steering system 212 cooperatively operates with the steeringcontroller 222 to control the steering of the vehicle. For example, if auser of the vehicle selects a certain track (route) to follow, thesteering controller 222 receives commands from a guidance system 230 andcontrols the steering system 212 such that the vehicle follows theselected route. Moreover, the steering controller 222 may control thesteering system 212 in a conventional manner when a user is manuallydriving. The steering system 212 may be an electrical steering system, adrive-by-wire steering system, an electro-hydraulic steering system, ora hydraulic steering system with an electronic control interface, forexample.

The vehicle data bus 210 provides signals to the steering controller 222from the display system 105. For example, the vehicle data bus 210 mayprovide signals including CAN messages to the steering controller 222.The messages may include, for example, commands such as steering anglecommands or position data.

The braking system 214 cooperatively operates with the brakingcontroller 224 to control the braking of the vehicle. For example, if auser of the vehicle selects a certain track (route) to follow, brakingcontroller 224 receives commands from the guidance system 230 andcontrols the braking system 214 to brake when the vehicle is approachinga turn. Moreover, the braking controller 224 may control the brakingsystem 214 in a conventional manner when a user is manually driving.

The propulsion controller 226 cooperatively operates with the propulsionsystem 216 to control the propulsion of the vehicle. The propulsion maybe any known motor or engine, for example. For example, if a user of thevehicle selects a certain track (route) to follow, propulsion controller226 receives commands from the guidance system 230 and controls thepropulsion system 216 to move the vehicle along the selected route.Moreover, the propulsion controller 226 may control the propulsionsystem 216 in a conventional manner when a user is manually driving.

As described above, the steering controller 222, braking controller 224and propulsion controller 226 communicate with the guidance system 230.The steering controller 222, braking controller 224 and propulsioncontroller 226 may communicate with the guidance system 230 through asecondary data bus or transmission line 235. The guidance system 230provides information to the steering controller 222, braking controller224 and propulsion controller 226 regarding location and route.Moreover, the guidance system 230 is connected to the vehicle data bus210 and obtains data and commands regarding which location and route tofollow, for example. The guidance system 230 may be a Global PositioningSystem (GPS) system or another type of guidance system.

The guidance system 230 may automatically steer the vehicle inaccordance with a path plan (e.g., linear path or contour) based on GPSposition measurements or navigation system measurements.

A location determining receiver 240 is connected to the vehicle data bus210, as well. The location determining receiver 240 may be a GPSreceiver, for example. The location determining receiver 240 transmitsthe location to the display system 105 and guidance system 230 throughthe vehicle data bus 210. The location-determining receiver 240 mayprovide one or more of the following data types: position data (e.g.,expressed as geographic coordinates), velocity data, and accelerationdata. Velocity data further comprises speed data and heading data forthe vehicle. The location determining receiver 240 transmits the data tothe display system 105 and guidance system 230 through the vehicle databus 210. The aforementioned data may further be displayed on the display115 of the display system 105.

The vehicle may include various actuators 220. For example, anelectrical steering system or a drive-by-wire steering system mayinclude an electric motor or actuator that is mechanically coupled torotate or steer at least one wheel of the vehicle.

As described, the display system 105, transmits and receives dataregarding the vehicle through the communications interface 110. Thecommunications interface is connected to a data bus 112. In addition tothe communications interface 110, the display 115 and the data bus 112,the display system 105 further includes a processor 120 and a datastorage device 125.

The communications interface 110, the display 115, the data bus 112, theprocessor 120 and the data storage device 125 are connected to the databus 112 and are configured to communicate through the data bus 112.

The processor 120 implements algorithms and other functionality of thedisplay system 105 described in further detail below.

The processor 120 may be any type of processor configured to executeprogram codes such as those stored in the data storage device 125.

In an example embodiment, the processor 120 may include an electronicdata processor, a digital signal processor, microprocessor, amicrocontroller, a programmable logic array, a logic circuit, anarithmetic logic unit, an application specific integrated circuit, adigital signal processor, a proportional-integral-derivative (PID)controller, or another data processing device.

The data storage device 125 may include any magnetic, electronic, oroptical device for storing data. For example, the data storage device125 may include an electronic data storage device, an electronic memory,non-volatile electronic random access memory, one or more electronicdata registers, data latches, a magnetic disc drive, a hard disc drive,an optical disc drive, or the like. The processor 120 outputs results ofalgorithms and other functionality of the display system 105 to the databus 112.

The data storage device 125 may store user profile data 126 andapplication module data 127. The user profile data 126 may include datarepresenting a skill level of the user and authorization level of theuser. For example, the skill level may be beginner, intermediate andadvanced. The application module data 127, which is Run Screen Module orsoftware module that is dedicated or programmed to perform, monitorand/or control a certain work task (e.g., planting, seeding, spraying,harvesting, leveling, tilling) of the work vehicle, includes data forthe display 115 to display run screens and organizes run screensaccording to sets, as will be described in further detail below.

The processor 120 includes a shortcut manager 121, emulator 122 and runscreen manager 123. The shortcut manager 121 manages the shortcutabilities of the display 115 such as the shortcut bar 116. The emulator122 emulates other buttons on the display 115 that were conventionallyrepresented by physical controls. With the shortcut manager 121, theemulator 122 emulates replaced user physical controls. The run screenmanager 123 retrieves run screens and sets of run screens based on anaction of the user. Moreover, the run screen manager 123 organizes therun screen modules into sets. The sets of run screen modules may bedictated by a user's selection and/or programmed by a manufacturer ofthe display system 105.

The display 115 may be a touch screen display with a user interface 117.The user interface 117 may act as a touch controller. The user interface117 may communicate the actions of the user (e.g., touch) to theprocessor 120 through the data bus 112. While actions by the user areoften described as touching, it should be understood that the userinterface 117 may operate based on voice commands and/or other objects(e.g., stylus) touching the display. Moreover, other possible gesturesinclude double tap, drag/slide, flick, nudge, pinch and spread. Thedisplay 115 displays the shortcut bar, status indicator 118 and runscreen 119, as is illustrated in FIGS. 2A-3B.

Run Pages

The terms run pages, run screens and dashboards may be usedinterchangeably.

At least one example embodiment discloses an edit run page set overlay.The edit run page set overlay may include design components for editinga current run page set. The edit run page set overlay gives the user theability to change the name of the current run page set and to add,remove, and reorder pages within the run page set.

A run screen provides a dedicated functionality or set of functions fora machine, such as planting, tilling, harvesting, spraying or anotheragricultural or other work task. Further, the run screen may providediagnostics, or status messages on different components, systems, or thevehicle, or its implements (attached or operable connected to thevehicle).

Run screens are customizable with modular content for the display ofvehicle status and control information. Run screens have customuser-programmable controls (e.g., guidance control) for vehiclecomponents, systems or features that previously required separatephysical controls (e.g., joystick, dials, levers, knobs or switches).Advantageously, the vehicle manufacturer does not need to providephysical controls for less popular or seldom ordered options on vehicles(e.g., front power take-off shaft on a tractor) because the displaysystem can be customized to produce data messages that emulate suchphysical controls in communication with the vehicle data bus 210 (e.g.,CAN data bus or ISO data bus).

The user may reprogram the vehicle to only have controls (icon buttonson the toolbar) that are relevant to a task at hand and the particularversion of the vehicle, for a particular user, or for a particularseason (e.g., harvesting buttons may be temporarily deleted for Springplanting, Fall Run screens can be optimized for harvesting, plantingwinter wheat or tillage; Spring Run Screens can be adjusted for tillage,fertilizing or planting; Summer Run Screens can be optimized forspraying).

FIGS. 2A-2B illustrate a set of run pages for a ten inch screenaccording to an example embodiment. FIGS. 3A-3B illustrate a set of runpages for a seven inch screen according to an example embodiment.

In FIG. 2A, a first run page for spraying is displayed on the display115. In FIG. 2B, a second run page for spraying is displayed on thedisplay 115. Edit page sets may be created by the run screen manager123. Each edit run page set may be associated with a function and/oruser. Example functions include planting, a spraying, and a harvesting.

The run screen manager 123 is configured to establish the set of runscreens in a temporal sequence for performing seasonal operations in anagricultural field.

Moreover, a set of run pages may include a Spring run page, a Summer runpage and a Fall run page, wherein each run page is associated with oneor more seasonal work tasks in the foregoing sequential order ofdisplay.

In an example embodiment, the first and second run pages are selected bythe user from a list consistent with a vehicle profile of the vehicle.In an example embodiment, the list is stored in the data storage device125 associated with the display 115. In another example embodiment,includes accessing the list is accessed via one of the vehicle data bus210 and the data bus 112 (ISO data bus).

In an example embodiment, the first and second run pages are selected bythe user from a list consistent with an implement profile for thevehicle. In an example embodiment, the implement profile is stored inthe data storage device 125 associated with the display 115. In anotherexample embodiment, the list is accessed via one of the vehicle data bus210 and data bus 112 (ISO data bus).

In an example embodiment, the first and second run pages are selected bythe user from a list consistent with a user profile of the vehicle. Inan example embodiment, the user profile is stored in the data storagedevice 125 associated with the display 115. In another exampleembodiment, includes accessing the list is accessed via one of thevehicle data bus 210 and data bus 112 (ISO data bus). The user profilescan be programmed to change with the seasons, such as having a Fall RunScreen, a Winter Run Screen and a Spring Run Screen and a Summer RunScreen.

In FIGS. 2A-2B, the user interface 117 produces a toggle 260 so a usermay toggle between run pages in the set of run pages. The toggle 260includes a right navigation button 260 b and a left navigation button260 a. The user touches the right navigation button 260 b to go to anext run page in the set. The taps the left navigation button 260 a to aprevious run page in the set. Since the run pages shown in FIGS. 2A-2Bare both directed to spraying the run pages may be in the same set.

Additionally, the user interface produces a short cut bar 270. The shortcut bar 270 includes one or more transient user-definable buttons 270a-270 n on the short cut bar 270. The buttons 270 a-270 n may beprogrammed by a manufacturer and then altered by the user. The short cutbar 270 is described in greater detail below.

The button 270 a opens an application for setting up a field operationby selecting vehicle, implement, field, and crop. The button 270 bindicates the state of field operation recording and allows the operatorto manually toggling the recording state on and off. The button 270 cindicates the state of the automatic guidance system and allows theoperator to toggle activation on and off. The button 270 d opens theautomatic guidance application. The button 270 e indicates the state ofthe automatic section control and opens the application for changingsettings for automatic section control. The button 270 f opens a ISO11783 part 6 virtual terminal application. The button 270 g opens theapplication that allows adjustment of display brightness and speakervolume. The button 270 n opens an on-line help application.

FIG. 2A illustrates a run page for spraying as applied produced by theuser interface 117. As shown, the user interface 117 produces a titletext area 252 and an identifier 250 for the field where the vehicle ispresent. Moreover, the display 115 shown in FIG. 2A includes a guidanceportion 255 which illustrates the current track and track spacing. Theuser interface 117 produces a map portion 265 which illustrates the pathof the vehicle.

In addition, the run page includes sections for fuel 267 and load depth269.

It should be understood, that the user interface 117 produces the fieldidentifier 250, the guidance portion 255 and the sections for fuel 267and load depth 269 by the user selecting the field identifier 250, theguidance portion 255 and the sections for fuel 267 and load depth 269 asparts of the run page for spraying. The operator may select differentcomponents to occupy the run page, including the option of leaving someareas unpopulated. The system ships with a standard set of run pagesdesigned to serve as a starting point for this customization.

FIG. 2B illustrates a run page for spraying overview produced by theuser interface 117. As shown in FIG. 2B the user interface 117 producesa guidance section 280. The guidance section 280 provides an overview ofthe current track and map of the vehicle. The user interface 117 alsoincludes an operating overview section 290 which displays an amount offuel remaining, a speed of the vehicle and amount of fuel used peramount of time, for example.

A section 285, including buttons 272 is an ISO 11783 part 6 virtualterminal application. A square central area of 480×480 pixels is a dataregion, while the area encompassing buttons 272 is a soft key region.

Multiple run pages may be grouped together into a run page set.

Because both displays in FIGS. 2A-2B illustrate spraying run pages, auser may group the spraying run pages into a run page set. Editing runpage sets is described in further detail below. A user may select a runpage by touching the title text area 252.

In FIGS. 3A-3B, the user interface 117 produces a toggle 360 so a usermay toggle between run pages in the set of run pages. Additionally, theuser interface produces a retractable short cut button 370. As will befurther described below, the retractable short cut bar includes one ormore transient user-definable buttons 270 a-270 n. The buttons may beprogrammed by a manufacturer and then altered by the user.

FIG. 3A illustrates a run page for spraying as applied produced by theuser interface 117. As shown, the user interface 117 produces anidentifier 350 for the field where the vehicle is present. Moreover, thedisplay 115 shown in FIG. 3A includes a guidance portion 355, whichillustrates the current track and track spacing. The user interface 117also produces a map portion 365 which illustrates the path of thevehicle and a coverage overview 370. The map portion 365 may be 480×480pixels.

It should be understood, that the user interface 117 produces the fieldidentifier 350, the guidance portion 355 and the coverage overview 370by the user selecting the field identifier 350, the guidance portion 355and the coverage overview 370 as parts of the run page for spraying.Alternatively, the run page may be established by the manufacturer.

FIG. 3B illustrates a run page for spraying overview produced by theuser interface 117. Section 386 illustrates a condensed guidance view.Section 388 illustrates a module displaying the status of the hydrauliccontrol valves. Pressing any of the vertical bars (I-V) will allow theuser to set the flow rate and duration for that valve. Section 390illustrates a rear hitch position and settings. Section 392 illustratesengine power as a function of full power. Sections 394 and 396 show avalue of machine parameters, including radar speed, wheel speed, fuellevel and diesel exhaust fluid (DEF) level. Section 398 illustrates aspeed for each field cruise setting.

Because both displays in FIGS. 3A-3B illustrate spraying run pages, auser may group the spraying run pages into a run page set. A user maynavigate through the run page set by pressing the navigation button 360.

As shown in FIGS. 2A-3B, the user interface 117 also produces a menubutton 262. When a user touches the menu button 262, the user interfacelaunches a menu stored in the data storage device 125 on the display115. The menu may include a list of applications to select such asguidance, reports work performed, vehicle monitoring and ISO(International Organization for Standardization) virtual terminal.

The user interface 117 is also configured to produce a statusinformation bar 264 and 364 in FIGS. 2A-2B and 3A-3B, respectively. Whena user touches one of the status information bars 264 and 364, the userinterface 117 launches a status center stored in the data storage device125. The status center stores data regarding messages, softwaredownloaded and network connections, such a Wi-Fi.

By using the user interface 117, a user may create, edit or delete a runpage; create, edit or delete a run page set; select a run page/run pageset to view; navigate through a run page set, access a menu, and viewstatus information.

By exchanging information with the user interface 117, the processor 120is configured to establish a first run screen associated with a firstfunction of a work vehicle and establish a second run screen associatedwith a second function of the work vehicle distinct from the firstfunction and define an order of appearance of the first run screen andthe second run screen within a set of run screens that allows a user toselect a run screen in the set of run screens that are displayable inaccordance with the defined order.

In example embodiment, the order of appearance is a user-definablesequence.

In example embodiment, the defining defines the order of appearance suchthat the order permits the user to toggle through the set of runscreens.

In example embodiment, the run screen manager 123 may select a run pageto delete from the set of run screens based on the user using the userinterface 117.

In example embodiment, the run screen manager 123 may add a third runscreen in any position within the set to change the order of appearanceof run screens within the set based on the user using the user interface117. The run screen manager 123 may change the order of the appearanceof the run screens within the set.

Retractable Toolbar

A retractable shortcut bar may be a component located at a bottom of ascreen. The retractable shortcut bar serves as a container for shortcutbuttons serving various user interface functions. The shortcut barallows one-touch access to commonly used functions of the vehicle. Theretractable shortcut bar allows for a display of state indicators andsystem toggles. The retractable shortcut bar allows for access tolow-take-rate vehicle and implement features without the costs andclutter of physical buttons.

In an example embodiment, the retracting feature allows the shortcut barto remain hidden, permitting use of a 480×480 pixel map module or a full480×480 pixel ISO 11783 part 6 virtual terminal.

As shown, in FIGS. 2A-2B, the shortcut bar 270 may be at the bottom ofthe display 115 in an example embodiment.

In an example embodiment, such as the seven inch screen shown in FIGS.3A-3B, a shortcut bar may be retractable. The terms, toolbar andshortcut bar, may be used interchangeably.

FIG. 4A illustrates an example embodiment of a screen with the shortcutbar retracted and FIGS. 4B-4C illustrate example embodiments of thescreen with the shortcut bar extended.

FIG. 4A illustrates a run page with a shortcut button 410. As shown inFIG. 4A, a shortcut bar is not extended.

FIG. 4B illustrates a shortcut bar 412 extended with two definablebuttons for tracking a vehicle's movement 415 and for GPS guidance alonga route 420. As shown, the shortcut bar 412 extends into a portion(e.g., first portion) of display area 425. The display area 425 may bedefined by a standard. For example, the display area 425 may be areserved area of 480 pixels by 480 pixels (e.g., second portion), whichis defined by ISO. Consequently, the shortcut bar 412 extends over aportion of the reserved area.

The shortcut bar 412 becomes extended upon the user pressing theshortcut button 410. Based on the user's action, the user interface 117communicates with the processor 120 to access the shortcut manager 121.The processor provides the user interface 117 with the data regardingthe shortcut bar 412, such as the buttons within the shortcut bar 412.As shown, when the shortcut bar 412 becomes extended, an “X” iconappears. By a user pressing the “X”, the user interface 117 retracts theshortcut bar 412. Additionally or alternatively, the shortcut bar 412disappears after a timer initiated at the time of deployment expiressuch that the second portion of the run screen is displayed.

FIG. 4C illustrates an example embodiment showing a shortcut bar 450with six definable buttons.

The processor 120 is configured to establish a run screen on the touchscreen display 115 that is associated with a function of a work vehicle.The processor 120 instructs the user interface 117 to configure the runscreen with a retractable toolbar. The retractable toolbar is deployedby the user interface in response to an action of a user of the touchscreen display and deployable over a first portion of the run screenupon the action of the user and otherwise hides to display a secondportion of the run screen, the second portion of the run screen being atleast a majority portion of the run screen.

As described in further detail below, the definable buttons may beprogrammed initially by the manufacturer and/or selected by the user.The buttons on the retractable toolbar 412 are associated with at leastone of the function and the run screen.

The processor is configured to allocate high priority status dataassociated with the function to a region other than the first portion ofthe run screen and allocate lower priority status data associated withthe function to first portion of the run screen. Consequently, the highpriority status data is not covered by the shortcut bar 412 is extended.

The user-definable buttons may be selected by the user and/or processor120 from at least one of a list and a menu based on status datadisplayed on the run screen.

The user-definable buttons may be selected by the user and/or processor120 from a list of options that are consistent with a vehicle profile ofthe vehicle. The vehicle profile may be stored in the data storagedevice 125 associated with the display.

The processor 120 may access the list of options through the vehicledata bus 210 and/or the data bus 112.

The user-definable buttons may be selected by the user and/or processor120 from a list of options consistent with the profile of the user.

A run screen provides a dedicated functionality or set of functions fora machine, such as planting, tilling, harvesting, spraying or anotheragricultural or other work task. Further, the run screen may providediagnostics, or status messages on different components, systems, or thevehicle, or its implements (attached or operable connected to thevehicle).

As described, when a user touches, taps, selects or activates theshortcut button 410, the toolbar is deployed with one or moreuser-definable buttons. The toolbar can be set to disappear after theexpiration of timer or only when closed by a user (e.g., by touching,tapping, selecting or activating a close “X” symbol). When the shortcutbar 412 is inactive, the user can enjoy the full screen to display otherinformation.

The user may use the toolbar or program it with links to customuser-programmable controls (e.g., run screens) for vehicle components,systems or features that previously required separate physical controls(e.g., joystick, dials, levers, knobs or switches). Advantageously, thevehicle manufacturer does not need to provide physical controls for lesspopular or seldom ordered options on vehicles (e.g., front powertake-off shaft on a tractor) because the display system 105 can becustomized to produce data messages that emulate such physical controlsin communication with the vehicle data bus (e.g., CAN data bus or ISOdata bus).

Status Shortcut

The status shortcut is a component that may be located on a shortcutbar. The status shortcut allows an operator to observe and/or toggle astatus of an application feature without opening the application. Thestatus shortcut may be added to the shortcut bar by a user.

The user interface 117 in conjunction with the processor 120 isconfigured to display buttons that provides both a status of a functionand control of the function.

FIGS. 5A-5E illustrate an example embodiment of a status shortcut buttonthat may be used in the shortcut bar 270 and the retractable shortcutbar 412. FIGS. 5A-5E illustrate various statuses of a guidance system,which is provided as button 270 c in FIG. 2A. The user interface 117adjusts the status of the buttons based on commands from the processor120. The processor 120 is configured to monitor that status of variousfunctions of the vehicle through the communications interface 110, asdescribed above.

FIG. 5A illustrates the status of the guidance system, when the guidancesystem is not installed. The icon in FIG. 5A is shown by the userinterface 117 in the shortcut bar when the guidance system is installedin a system of the vehicle.

FIG. 5B illustrates the status of the guidance system, when the guidancesystem is installed. The icon in FIG. 5B is shown by the user interface117 in the shortcut bar when the guidance system is installed in asystem of the vehicle.

FIG. 5C illustrates the status of the guidance system, when the guidancesystem is configured. The icon in FIG. 5C is shown by the user interface117 in the shortcut bar when the guidance system is setup in the systemof the vehicle. This includes specific routes, guidance the vehicle isto follow and/or spacing the vehicle is to follow, for example.

FIG. 5D illustrates the status of the guidance system, when the guidancesystem is enabled. The guidance system is enabled when inputs are madeand the guidance system may be activated by pushing the button 270 c.

FIG. 5E illustrates the status of the guidance system, when the guidancesystem is activated. The icon in FIG. 5E indicates that the guidancesystem is in use. The user interface 117 shows the icon in FIG. 5E untilthe user deactivates the guidance system, touches the steering wheel orother conditions (e.g., out of seat, off GPS path, etc.). For example,the user interface 117 may transition from the icon shown in FIG. 5E tothe icon shown in FIG. 5D when the user pushes the button 270 c todisengage the guidance system.

In an example embodiment, a different icon may be displayed if theguidance system is off.

The icons of FIGS. 5A-5E may transition in response to a status messagedata provided by the location-determining receiver 240 and the guidancesystem 230.

In addition to the guidance system 230, icons may represent the statusof at least one of planting, plowing, spraying and harvesting.

The processor 120 is configured to establish a run screen associatedwith a first function of a vehicle, provide a location-determiningreceiver for potential guidance of the work vehicle, establish aplurality of performance states associated with at least one of thelocation-determining receiver and a guidance controller and display oneor more of the performance states by corresponding visually displayablestates without changing to another screen of the display.

The processor 120 may issue a call from the display system 105 to theguidance system 230, wherein the transition of the icon occurs inresponse to data transmitted from the guidance system 230 in reply tothe call.

In an example embodiment, the guidance system 230 is one of (1)continuously active in a background data processing of the displaysystem and (2) loaded into the data storage device 125 for the dataprocessor.

The location-determining receiver 240 is coupled directly or indirectlyto the vehicle data bus 210 to support communications with the displaysystem 105. The display system 105 can run multiple applications in thebackground and may use any suitable windowing operating system. For theguidance system 230 shortcut status, the status can be retrieved anddisplayed in the button (e.g., 5 different states possible) on theshortcut bar 270 or 412. The status is displayed without displaying theentire guidance system 230 screen. A call regularly (e.g., after theexpiration of a time interval) made to a guidance system softwaremodule, a guidance system program module or subroutine requests theupdate of status information for the shortcut button.

Referring back to FIGS. 2A-2B and 3A-3B, when a user presses the menubutton 262, the processor 120 retrieves the menu from the data storagedevice 125. The processor 120 then provides the display with the menu,which is shown in FIG. 6. As shown in FIG. 6, the user may selectsettings, applications, implements or system information to display. InFIG. 6, applications are selected for display.

By using the user interface 117, a user may select one of theapplications being displayed. In an example embodiment, the user selectsa dashboard layout manager application to may create, edit or delete arun page; create, edit or delete a run page set; select a run page/runpage set to view; and navigate through a run page set.

When a user touches a dashboard layout manager 610, the user interface117 provides the processor 120 with the user's selection. The run screenmanager 123, within the processor 120, retrieves a layout managerapplication from the data storage 125. The processor 120 then providesthe display 115 with a layout manager display, shown in FIG. 7A.

As shown in FIG. 7A, the user interface 117 provides the user theability to select dashboard sets 710 a, shortcut bars 710 b or dashboardlibraries 710 c for display. FIG. 7A illustrates an embodiment where thedashboard sets are shown in a display area 725, FIG. 7B illustrates anembodiment with the short cut bars are shown in the display area 725 andFIG. 7C illustrates an embodiment with the dashboard library shown inthe display area 725.

With the dashboard sets display shown in FIG. 7A, the user may add a newdashboard set by pressing a button 730, duplicate a dashboard set bypressing a button 735, or edit a dashboard set by pressing an editbutton 740. The user interface 117 displays the edit button 740 when auser touches one of the dashboard sets displayed in the display area725. If the user selects the edit button 740, the processor 120retrieves an edit dashboard set overlay shown in FIG. 9A. The editing ofa dashboard is also described in greater detail below, with reference toFIGS. 10A-10J.

When a user selects to add a new dashboard set, the user interface 117provides the processor 120 with the user's selection. The processor 120retrieves the dashboard set management overlay and provides thedashboard set management overlay to the user interface 117, which isillustrated in FIGS. 9A-9C. The selection of the button 730, causes thedisplay 115 to display the screen shown in FIG. 9B.

When a user selects to duplicate a dashboard set, the user interface 117provides the processor 120 with the user's selection. The selection ofthe button 735 causes the processor 120 to provided data to the displayto display the screen shown in FIG. 9C.

FIGS. 9A-9C are described in greater detail below.

Referring back to FIG. 2A, when a user presses the title text area 252,the processor 120 retrieves select dashboard data from the data storagedevice 125. The processor 120 then provides the display 115 with theselect dashboard data, which is shown in FIG. 8.

As shown in FIG. 8, the user may select may select a dashboard withinthe run page set. The run page set is identified in area 810 and a usermay select one of the run pages 815 a, 815 b and 815 c that aredisplayed by the display 115. By tapping one of the run pages 815 a, 815b and 815 c, the user interface 117 provides the processor 120 with theuser's selection. This causes the processor 120 to retrieve the selectedrun page and provide the selected run page to the display 115. If theuser selects an edit button 810 (e.g., by touching), the user interface117 provides the processor 120 with the user's selection. This causesthe processor 120 to retrieve the dashboard set management overlay,which is illustrated in FIGS. 9A-9C. The selection of the button 810,causes the display 115 to display the screen shown in FIG. 9A.

As shown in FIG. 9A, a user may edit the dashboard set name by touchingarea 910, select a shortcut bar to use with dashboard set by touchingarea 920, edit, add, duplicate, remove or reorder the dashboards. Theprocessor 120 removes the dashboard set from the data storage device 125when a user presses a delete button 930. When the user touches thetouching area 920, the processor 120 is configured to provide the userwith a list of shortcut bars the user may select for the dashboard set.Upon selecting a shortcut bar, the processor 120 assigns the selectedshortcut bar to the dashboard set and the user interface 117 returns tothe display in FIG. 9A.

When a user selects a dashboard from a list of dashboards 917, the userinterface produces an edit button 935, a duplicate button 940, a reorderbutton 945 and a delete button 950. To add a dashboard to the dashboardset, the user presses button 955. Consequently, the user may adddashboards to a set according to factors such as season and job type,for example. The dashboards are saved in the data storage device 125.

The user may reorder the dashboards within the set by pressing theup/down arrows in the reorder button 945.

FIGS. 9B-9C illustrate similar functions as those shown in FIG. 9Aexcept FIGS. 9B-9C are for new dashboard sets. Thus, for the sake ofbrevity, FIGS. 9B-9C will not be described in greater detail.

FIGS. 10A-10J illustrates an example embodiment of adding and editing adashboard for a 7×7 display.

As described above, when a user selects to add a new dashboard, the userinterface 117 via the processor 120, produces the display shown in FIG.10A.

When creating a new dashboard, a module area 1005 is initially blank.The new dashboard includes the menu icon 262, the retractable shortcutbutton 370 and a save button 1002. When the user interface 117 sensesthat the save button 1002 has been touched, the processor 120 saves thedashboard. The processor 120 is configured to retrieve and add moduleoverlay when the user selects the add module button 1010. The add moduleoverlay is shown in FIG. 10B.

The user interface 117 produces tabs 1015 a, 105 b, 1015 c and 1015 d inthe add module overlay to select among recently used modules, tractorcontrols, applications and system modules.

The recently used modules tab 1015 a contains any dashboard module thathave been added to or removed from a dashboard during a session. Forexample, a session may be a period of time from a last restart to a nextrestart. The contents of the recently used tab 1015 a may be sorted witha most recently used dashboard module at the top.

A content area 1020 of each tab contains a title icon grid with iconsfor each type of dashboard module that is available within thatcategory.

In the add module overlay shown in FIG. 10B, the user interface 117displays a list of tractor controls in the content area 1020.

When a module is selected, the processor 120 retrieves an add moduletype overlay. FIG. 10C illustrates a module type overlay for asingle-valve overview.

In FIG. 10C, the user interface 117 produces a picture of the dashboardmodule 1025, a graphic to show the size of the dashboard module 1030, adescription of the elements within the dashboard module and an addbutton. The processor 120 determines what space the dashboard module mayfit into the dashboard. If the dashboard module will not fit in anyavailable space of the dashboard, the user interface 117 produces amessage and icon with the module graphic to notify the user.

When the user selects the add button 1035, the processor 120 adds theselected module to the run screen by using the run screen manager 123and returns to the new dashboard or edit dashboard overlay, as shown inFIG. 10D.

In FIG. 10D, the user interface 117 produces the new dashboard overlaywith the selected module. Moreover, the user interface 117 provides theuser with buttons for moving 1065 and adding a module 1010 in a messagearea frame 1060. To move a module 1065, the user may select the module1065 by touching it. The user may move the module 1065 by dragging themodule 1065 to a location within the area 1005.

When the user has finished moving the module 1065, the user interface117 changes the message area frame 1606 to include a remove button 1067,as shown in FIG. 10E. The user may also edit the dashboard name byentering a name in the dashboard name area 1070. To deselect the module1065, the user touches the display 117 anywhere except on the module1065, which returns the user interface to the user interface to FIG.10F.

A user may continue the same process to add more dashboard modules untilthe module area 1005 is filled.

When the processor 120 senses that an edit dashboard button is selected,the processor 120 causes the user interface 117 to display an editdashboard overly shown in FIG. 10G.

The user may select a dashboard module by touching the dashboard module.For example, the user may touch the field module 1070. By sensing theuser's selection, the processor 120 provides data to and instructs theuser interface 117 to allow the user to move or delete the selectedfield module 1070, as shown in FIG. 10H. If there is no space to movethe selected module, the user interface notifies the user that no spaceis available, as shown in FIG. 10I.

In FIG. 10J, a portion of the display is removed by the processor 120,which allows a user to move the field module 1070, when the field module1070 is selected by the user. To deselect the field module 1070, theuser taps anywhere on the dashboard except on the module 1070.

With the shortcut bars display shown in FIG. 7B, the user may add a newshortcut bar by pressing a button 745, duplicate a shortcut bar bypressing a button 750, or edit a shortcut bar set by pressing an editbutton 760. The user interface 117 display the edit button 760 when auser touches one of the shortcut bars displayed in the display area 725.If the user selects the edit button 760, the processor 120 retrieves anedit shortcut bar overlay. The editing of a shortcut bar is described ingreater detail below, with reference to FIGS. 11A-11E.

When a user selects to add a new shortcut bar or duplicate a shortcutbar, the user interface 117 provides the processor 120 with the user'sselection.

If the user selects a shortcut bar edit button, the processor 120retrieves the edit shortcut bar overlay. FIG. 11A illustrates an exampleedit shortcut bar overlay.

As shown in FIG. 11A, the user interface 117 displays a name of theshortcut bar in area 1102. The shortcut bar name may be change bypressing the edit button 1104. The user interface 117 may display akeyboard for the user to use to change the name of the shortcut bar.

The user interface 117 also displays a graphic of the shortcut bar 1106.When a shortcut bar is not filled by shortcuts, empty spaces of theshortcut bar are displayed as add shortcut buttons 1108. Moreover,shortcuts within the shortcut bar 1106 may be moved in a similar manneras the dashboard modules. In other words the shortcuts within theshortcut bar 1106 may be moved by pressing and sliding the shortcut toan empty area of the shortcut bar.

The user interface 117 also illustrates an assigned dashboard setsbutton 1112. By a user pressing the assigned dashboard sets button 1112,the processor 120 permits the user to view and edit the dashboard setswhere the shortcut bar is used.

The processor 120 saves the shortcut bar in the data storage 125 when auser presses a save button 1114. The shortcut manager 121 manages thestorage of the shortcut bars.

Moreover, by pressing a shortcut, the user interface 117 highlights thepressed shortcut and displays a remove shortcut button 1110, whichpermits a user to delete the shortcut from the shortcut bar, as shown inFIG. 11B.

When a user selects to add a new shortcut bar, the user interface 117provides the processor 120 with the user's selection. The processor 120provides the user interface 117 with data to display a new shortcut baroverlay, as shown in FIG. 11C. The functionality of the user interface117 with respect to the new shortcut bar overlay is the same as thefunctionality with respect to the edit shortcut bar overlay. Thus, forthe sake of brevity, FIG. 11C will not be described in greater detail.

When a user selects to duplicate a new shortcut bar, the user interface117 provides the processor 120 with the user's selection. The processor120 provides the user interface 117 with data to display a duplicateshortcut bar overlay, as shown in FIG. 11D. The functionality of theuser interface 117 with respect to the new shortcut bar overlay is thesame as the functionality with respect to the edit shortcut bar overlay.Thus, for the sake of brevity, FIG. 11D will not be described in greaterdetail.

The processor 120 saves the duplicated shortcut bar in the data storage125 when a user presses a save button 1114. The shortcut manager 121manages the storage of the shortcut bars.

When a user presses the add a shortcut button 1108 in either the editshortcut bar overlay or the new/duplicate shortcut bar overlay, theprocessor 120 provides the user interface 117 to display an add shortcutoverlay, as shown in FIG. 11E.

The user interface 117 produces tabs 1115 a, 115 b and 1115 c in the addshortcut overlay to select among recently used modules, tractor settingsand system shortcuts.

The recent used shortcuts tab 1115 a contains any shortcut that havebeen added to or removed from a shortcut bar during a session.

For example, a session may be a period of time from a last restart to anext restart. The contents of the recently used tab 1115 a may be sortedwith a most recently used dashboard module at the top.

A content area 1120 of each tab contains a title icon grid with iconsfor each type of shortcut that is available within that category.

In the add shortcut overlay shown in FIG. 11E, the user interface 117displays a list of application shortcuts in the content area 1120. Whena user selects a shortcut to add, the processor 120 adds the shortcut tothe shortcut bar and provides the user interface 117 to display anupdate shortcut bar with the selected shortcut bar in either thenew/duplicate shortcut bar overlay or edit shortcut bar overlay.

Example embodiments being thus described, it will be obvious that thesame may be varied in many ways. Such variations are not to be regardedas a departure from the spirit and scope of example embodiments, and allsuch modifications as would be obvious to one skilled in the art areintended to be included within the scope of the claims.

What is claimed is:
 1. A method for managing a display of a displaysystem, the method comprising: establishing a run screen associated witha first function of a work vehicle; providing a location-determiningreceiver for potential guidance of the work vehicle; establishing aplurality of performance states associated with at least one of thelocation-determining receiver and a guidance controller; and displayingone or more of the performance states by corresponding visuallydisplayable states without changing to another screen of the display. 2.The method of claim 1, wherein the corresponding visually displayablestates are displayed on an icon on the run screen, the correspondingvisually displayable states being different transitions of the icon. 3.The method according to claim 2, further comprising: changing thetransition of the icon in response to a user command entered into atouch screen display.
 4. The method according to claim 2, furthercomprising: changing the transition of the icon in response to statusmessage data provided by the at least one of the location-determiningreceiver and the guidance controller.
 5. The method according to claim2, further comprising: issuing a call from a display operating system toa guidance program module, wherein the transition of the icon occurs inresponse to data transmitted from the guidance program module in replyto the call.
 6. The method according to claim 5, wherein the guidanceprogram module is one of (1) continuously active in a background dataprocessing of the display system and (2) loaded into executable memoryfor the data processor.
 7. The method according to claim 6, wherein thedata transmitted in reply to the call is available with low latency. 8.The method according to claim 1, further comprising: changing thecorresponding visually displayable state in response to a user commandentered into a touch screen display.
 9. The method according to claim 1,further comprising: changing the corresponding visually displayablestate in response to status message data provided by the at least one ofthe location-determining receiver and the guidance controller.
 10. Themethod of claim 1, wherein the performance states are installed,configured, enabled and activated.
 11. The method of claim 1, whereinthe first function is one of planting, plowing, spraying and harvesting.12. A data processor for managing a display of a display system, thedata processor configured to, establish a run screen associated with afirst function of a work vehicle; provide a location-determiningreceiver for potential guidance of the work vehicle; establish aplurality of performance states associated with at least one of thelocation-determining receiver and a guidance controller; and display oneor more of the performance states by corresponding visually displayablestates without changing to another screen of the display.